Skip to content

Conversation

@alamb
Copy link
Contributor

@alamb alamb commented Oct 27, 2025

This is a test to show that the new CI trigger in

Will properly catch incorrect datafusion-pin updates

@github-actions github-actions bot added the development-process Related to development process of DataFusion label Oct 27, 2025
@alamb alamb changed the title [DO NOT MERGE] Test pinning datafusion-testing backwards [DO NOT MERGE] Test pinning datafusion-testing backwards w/ new CI check Oct 27, 2025
github-merge-queue bot pushed a commit that referenced this pull request Oct 30, 2025
…18310)

## Which issue does this PR close?



## Rationale for this change

The `extended` tests rely on the checkout of datafusion-testing (that
has the expected results for the sqlite sqllogictest suite)

However, we don't currently run the extended tests when that pin is
changed so we could potentially break CI on main if we don't catch
changes in code review (this just happened to me in
#17866 (review))

## What changes are included in this PR?

1. Run extended CI tests on changes to datafusion-testing 



## Are these changes tested?

I tested this in PR
- #18311
- #18312

## Are there any user-facing changes?
No
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

development-process Related to development process of DataFusion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant